CVE-2025-32878

The COROS PACE 3 GPS sports watch, running firmware versions through 3.0808.0 , is vulnerable to a man-in-the-middle (MitM) attack due to improper certificate validation . The device fails to validate the X.509 server certificate during the TLS handshake when requesting firmware information from ...

CVE-2025-48706

The COROS PACE 3 GPS sports watch is vulnerable to an out-of-bounds read vulnerability in versions through 3.0808.0 . An attacker can send a crafted Bluetooth Low Energy (BLE) message to the device, which triggers a forced reboot . To remediate this issue, users are recommended to update the CORO...

CVE-2025-48705

A NULL pointer dereference vulnerability exists in the COROS PACE 3 GPS sports watch, affecting versions 3.0808.0 and earlier. By sending a crafted BLE message , an attacker can force the device to reboot . As a temporary workaround, users are advised to restrict the reception of BLE messages fro...

CVE-2025-32877

The COROS PACE 3 GPS sports watch is vulnerable in versions through 3.0808.0 due to a flaw in the Bluetooth pairing method. The device incorrectly identifies itself as having no input or output capabilities, forcing the use of the Just Works pairing method. Because this method lacks authenticatio...

CVE-2025-32879

The COROS PACE 3 GPS sports watch (versions 3.0808.0 and earlier) is vulnerable to an improper authentication issue in its Bluetooth Low Energy (BLE) services. The device starts advertising if no other device is connected, allowing an attacker to establish a connection. Because the BLE services a...

CVE-2025-32880

The COROS PACE 3 GPS sports watch, running firmware versions through 3.0808.0 , is vulnerable to sniffing and machine-in-the-middle (MitM) attacks. The root cause is that the device downloads firmware files via unencrypted HTTP when connected to a WLAN. An attacker positioned between the device a...

CVE-2025-32876

The COROS PACE 3 GPS sports watch, running firmware versions 3.0808.0 and prior , is vulnerable to communication eavesdropping due to a flaw in its BLE implementation . The device fails to support LE Secure Connections and instead enforces BLE Legacy Pairing . Because the Just Works pairing metho...